Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dbb1fa16446f42efae9abd140caf95e99488efd5a1d6857a977c31f8a8d99cfb

Tx prefix hash: 8f4c7088662e35c62c9d121f1ff85e47ae629b498d8603c136d4571f18b4961f
Tx public key: b89002f10197f3bdbe9d4f0e7bee3c10869daccf40cecb534adb261d2262ed4a
Timestamp: 1697214431 Timestamp [UCT]: 2023-10-13 16:27:11 Age [y:d:h:m:s]: 01:249:17:37:11
Block: 868849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439431 RingCT/type: yes/0
Extra: 01b89002f10197f3bdbe9d4f0e7bee3c10869daccf40cecb534adb261d2262ed4a021100000004faf35c9c000000000000000000

1 output(s) for total of 0.811227409000 dcy

stealth address amount amount idx
00: eeeaa3d933c7f004b0252852120caf3287c4faf307a53280f4c526e8c67499a1 0.811227409000 1323668 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 868859, "vin": [ { "gen": { "height": 868849 } } ], "vout": [ { "amount": 811227409, "target": { "key": "eeeaa3d933c7f004b0252852120caf3287c4faf307a53280f4c526e8c67499a1" } } ], "extra": [ 1, 184, 144, 2, 241, 1, 151, 243, 189, 190, 157, 79, 14, 123, 238, 60, 16, 134, 157, 172, 207, 64, 206, 203, 83, 74, 219, 38, 29, 34, 98, 237, 74, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8