Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1efb72e81e61c6f9c984679ef0bf6ad1cc9f4070a00ed73a92cfb6affe9dcdc9

Tx prefix hash: edc9b02dad6ac02f451b8907c6b1614f94d19a881fbba50fa1e07f283bec0784
Tx public key: 9854771b9dba0ee2eea2fed6470952c5999b5af7d0594e458b3b2cfd65e6c729
Timestamp: 1726422305 Timestamp [UCT]: 2024-09-15 17:45:05 Age [y:d:h:m:s]: 00:210:11:57:49
Block: 1110796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150295 RingCT/type: yes/0
Extra: 019854771b9dba0ee2eea2fed6470952c5999b5af7d0594e458b3b2cfd65e6c729021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3bd65fd2ebf23e54e7ade65752e27e264ad313ed808599f75f5802ac40d0332 0.600000000000 1589531 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": 1110806, "vin": [ { "gen": { "height": 1110796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3bd65fd2ebf23e54e7ade65752e27e264ad313ed808599f75f5802ac40d0332" } } ], "extra": [ 1, 152, 84, 119, 27, 157, 186, 14, 226, 238, 162, 254, 214, 71, 9, 82, 197, 153, 155, 90, 247, 208, 89, 78, 69, 139, 59, 44, 253, 101, 230, 199, 41, 2, 17, 0, 0, 0, 5, 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