Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30015bd9183e5d4e652c8d544042efcc65d01f1eac2e54b6c9bf7473237b4b1a

Tx prefix hash: e8945e0ef1792d43f871d44213b82827096f926d034c72097c2a87395f50b719
Tx public key: 3f28b51c2005ea88c0bea431eff4126bdc016c5d3f1c3d605a49188b9cd1a5c0
Timestamp: 1744053903 Timestamp [UCT]: 2025-04-07 19:25:03 Age [y:d:h:m:s]: 00:277:19:45:22
Block: 1256462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196381 RingCT/type: yes/0
Extra: 013f28b51c2005ea88c0bea431eff4126bdc016c5d3f1c3d605a49188b9cd1a5c0021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aa2cc389986f2ec01b6b51872847e82061517a3d1dbdd08170bdd57d8f89a2c 0.600000000000 1743575 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": 1256472, "vin": [ { "gen": { "height": 1256462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa2cc389986f2ec01b6b51872847e82061517a3d1dbdd08170bdd57d8f89a2c" } } ], "extra": [ 1, 63, 40, 181, 28, 32, 5, 234, 136, 192, 190, 164, 49, 239, 244, 18, 107, 220, 1, 108, 93, 63, 28, 61, 96, 90, 73, 24, 139, 156, 209, 165, 192, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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