Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eec10f4ed8be5c307f5210bbd8a53147ba7dc7a748d82ad78bd915d348505234

Tx prefix hash: 36e44a3d9dab0aab34fedf24c8caaae61802e7cdcd2b8c9c5cce975f92dc6685
Tx public key: 66a0cf3e5f028992668fb7c661792b311a2c9104b0afa85eefbef197f234ad33
Timestamp: 1735016638 Timestamp [UCT]: 2024-12-24 05:03:58 Age [y:d:h:m:s]: 00:098:22:10:14
Block: 1181936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70470 RingCT/type: yes/0
Extra: 0166a0cf3e5f028992668fb7c661792b311a2c9104b0afa85eefbef197f234ad330211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0451808705f791670bd83eada7a3e0ea05c6346c373142820d4b1a133b19059d 0.600000000000 1668365 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": 1181946, "vin": [ { "gen": { "height": 1181936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0451808705f791670bd83eada7a3e0ea05c6346c373142820d4b1a133b19059d" } } ], "extra": [ 1, 102, 160, 207, 62, 95, 2, 137, 146, 102, 143, 183, 198, 97, 121, 43, 49, 26, 44, 145, 4, 176, 175, 168, 94, 239, 190, 241, 151, 242, 52, 173, 51, 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