Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86fad2ea723f8fbd069d9507ba0ca9a8e00d754223be79b831f99c8d42814e9d

Tx prefix hash: 24426e1f58a67a714eb6a4d44a45e44a4a32e742c79565c8a5d8e379c2944533
Tx public key: cfc29eac53c1f8095f935bf6a3f0a214434ccd495de412cdd95e822081797adf
Timestamp: 1746051594 Timestamp [UCT]: 2025-04-30 22:19:54 Age [y:d:h:m:s]: 00:245:06:56:29
Block: 1273008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173089 RingCT/type: yes/0
Extra: 01cfc29eac53c1f8095f935bf6a3f0a214434ccd495de412cdd95e822081797adf0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33a1c0efbe7345c9f0caec92450c19a2a88866a56a35650680d6e441aebb53f1 0.600000000000 1760285 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": 1273018, "vin": [ { "gen": { "height": 1273008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33a1c0efbe7345c9f0caec92450c19a2a88866a56a35650680d6e441aebb53f1" } } ], "extra": [ 1, 207, 194, 158, 172, 83, 193, 248, 9, 95, 147, 91, 246, 163, 240, 162, 20, 67, 76, 205, 73, 93, 228, 18, 205, 217, 94, 130, 32, 129, 121, 122, 223, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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