Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 189f0b28b8becf1b097da86d7824d915a5bdab60dc6dc88dd8f1767355c7d86c

Tx prefix hash: 263e14e67991bf77cdeacfb2eb6e6d70ebea557e8a4df352ad753a7be7ee569e
Tx public key: 2560d6b3db98afee3cb01a4065093ed060c3db2e134fc2ff68c7db84b220d27a
Timestamp: 1736242829 Timestamp [UCT]: 2025-01-07 09:40:29 Age [y:d:h:m:s]: 00:100:02:46:35
Block: 1192088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71330 RingCT/type: yes/0
Extra: 012560d6b3db98afee3cb01a4065093ed060c3db2e134fc2ff68c7db84b220d27a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3091f0cc815c30f99cba86d644c6db2cfee5b9818c3f3fb19de6741e613c256f 0.600000000000 1678633 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": 1192098, "vin": [ { "gen": { "height": 1192088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3091f0cc815c30f99cba86d644c6db2cfee5b9818c3f3fb19de6741e613c256f" } } ], "extra": [ 1, 37, 96, 214, 179, 219, 152, 175, 238, 60, 176, 26, 64, 101, 9, 62, 208, 96, 195, 219, 46, 19, 79, 194, 255, 104, 199, 219, 132, 178, 32, 210, 122, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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