Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fe9ba2c87e0242f65d1bb414917daf3561ad35bbb9beae3047f770af9fbbb37

Tx prefix hash: 3492ab8341cc550a713e6d40769b753bce3bb99be8be3a7538bcdfa5abf86125
Tx public key: e18063fc08703a24b19ce4e76da9c2306ad8a75f0a14a88c6108e94ce03c613f
Timestamp: 1723264506 Timestamp [UCT]: 2024-08-10 04:35:06 Age [y:d:h:m:s]: 00:242:01:21:26
Block: 1084618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172879 RingCT/type: yes/0
Extra: 01e18063fc08703a24b19ce4e76da9c2306ad8a75f0a14a88c6108e94ce03c613f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b559c4d6bb0b15dc891b7c5688c8878b682b605287b9170cbaa25936089a2d88 0.600000000000 1558959 of 15

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": 1084628, "vin": [ { "gen": { "height": 1084618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b559c4d6bb0b15dc891b7c5688c8878b682b605287b9170cbaa25936089a2d88" } } ], "extra": [ 1, 225, 128, 99, 252, 8, 112, 58, 36, 177, 156, 228, 231, 109, 169, 194, 48, 106, 216, 167, 95, 10, 20, 168, 140, 97, 8, 233, 76, 224, 60, 97, 63, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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