Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c79278f2aba72a1fb4f3bccab9c32886947a6d8a30baca4f4828083644f7de

Tx prefix hash: e75ca876c0ac71a37a8c57142d7e742306c556191a4207b3a791bd40b5fd9adc
Tx public key: cc038671ba847b847d1074f68a4a8e7b9439c2dd4d2596d8a692abd6b0bec6dc
Timestamp: 1736674221 Timestamp [UCT]: 2025-01-12 09:30:21 Age [y:d:h:m:s]: 00:074:17:48:41
Block: 1195651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53186 RingCT/type: yes/0
Extra: 01cc038671ba847b847d1074f68a4a8e7b9439c2dd4d2596d8a692abd6b0bec6dc0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfb2ad427c1cee530ece53d94b33295263c59d5a0db17f0c98694f8566dcd04a 0.600000000000 1682242 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": 1195661, "vin": [ { "gen": { "height": 1195651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfb2ad427c1cee530ece53d94b33295263c59d5a0db17f0c98694f8566dcd04a" } } ], "extra": [ 1, 204, 3, 134, 113, 186, 132, 123, 132, 125, 16, 116, 246, 138, 74, 142, 123, 148, 57, 194, 221, 77, 37, 150, 216, 166, 146, 171, 214, 176, 190, 198, 220, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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