Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3379d332e99310d5df163592d79cca56ebf6a764127eeee0735cd5efd869173a

Tx prefix hash: cd36e5eafe7d6193eff94d30e7ac76f7f95c5ebf3fb83955f77c401e2c7fa7d5
Tx public key: ba9ae4c3892e90e8c3aa240bc21d1f5816bb175eeac9e79fc0ad1b238c333af7
Timestamp: 1751275384 Timestamp [UCT]: 2025-06-30 09:23:04 Age [y:d:h:m:s]: 00:136:14:35:11
Block: 1315750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95827 RingCT/type: yes/0
Extra: 01ba9ae4c3892e90e8c3aa240bc21d1f5816bb175eeac9e79fc0ad1b238c333af70211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 940fc31b694fcef09ad385194dbca0b8f02872d38d34fd1ad093d23b45ac3b9f 0.600000000000 1803405 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": 1315760, "vin": [ { "gen": { "height": 1315750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "940fc31b694fcef09ad385194dbca0b8f02872d38d34fd1ad093d23b45ac3b9f" } } ], "extra": [ 1, 186, 154, 228, 195, 137, 46, 144, 232, 195, 170, 36, 11, 194, 29, 31, 88, 22, 187, 23, 94, 234, 201, 231, 159, 192, 173, 27, 35, 140, 51, 58, 247, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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