Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a75c70df75b364c821df1fafa1d6b2fda67d10cbf397eb3dbb1c7ed1e6ba7d6

Tx prefix hash: db9d1834762231c05e11dd4f5983e2695e585b793e7c083fc8e5c468d2359cf7
Tx public key: 179d6138d3ddff802f2b78d6a6370596e31d827df6d224a93bba0a76ecbe407c
Timestamp: 1710456645 Timestamp [UCT]: 2024-03-14 22:50:45 Age [y:d:h:m:s]: 01:035:16:22:51
Block: 978459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286473 RingCT/type: yes/0
Extra: 01179d6138d3ddff802f2b78d6a6370596e31d827df6d224a93bba0a76ecbe407c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf0cb3d841a653a8f070b368a5f5718e2c2db72a1405c05d043f0006bb3308fa 0.600000000000 1438486 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": 978469, "vin": [ { "gen": { "height": 978459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf0cb3d841a653a8f070b368a5f5718e2c2db72a1405c05d043f0006bb3308fa" } } ], "extra": [ 1, 23, 157, 97, 56, 211, 221, 255, 128, 47, 43, 120, 214, 166, 55, 5, 150, 227, 29, 130, 125, 246, 210, 36, 169, 59, 186, 10, 118, 236, 190, 64, 124, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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