Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 743ee135fedf49a33ad964e48849fb5e229aa2560628d550f132f05abae94e7f

Tx prefix hash: e5e951adb73c38b644b03c56fcb17bc231f306317e6f87cdcb6fac6c340e610b
Tx public key: 3d46d695d0964dced6d6e8f4adc85ba903bd14bcc76e5dbc213f23a83035632d
Timestamp: 1702944613 Timestamp [UCT]: 2023-12-19 00:10:13 Age [y:d:h:m:s]: 01:110:13:54:17
Block: 916160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340156 RingCT/type: yes/0
Extra: 013d46d695d0964dced6d6e8f4adc85ba903bd14bcc76e5dbc213f23a83035632d02110000000de6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1075c845a289c7095c9cabeb4ee586453b2c7358173c095444e8ae925a90a2b5 0.600000000000 1373642 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": 916170, "vin": [ { "gen": { "height": 916160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1075c845a289c7095c9cabeb4ee586453b2c7358173c095444e8ae925a90a2b5" } } ], "extra": [ 1, 61, 70, 214, 149, 208, 150, 77, 206, 214, 214, 232, 244, 173, 200, 91, 169, 3, 189, 20, 188, 199, 110, 93, 188, 33, 63, 35, 168, 48, 53, 99, 45, 2, 17, 0, 0, 0, 13, 230, 210, 127, 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