Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3dcd42ed7b71d256a25139b9af2b654eb719395c38a9d023ea410c464ea5e44

Tx prefix hash: 07017903e9f655022897427ea9e5aeec1217a02b94f62471ce6cfd3e1639dd96
Tx public key: e324f2de772be65aa9bebcb0ebf783c2e3074188804b3ac0bce92dd289c912f2
Timestamp: 1712403004 Timestamp [UCT]: 2024-04-06 11:30:04 Age [y:d:h:m:s]: 01:048:15:01:12
Block: 994541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295776 RingCT/type: yes/0
Extra: 01e324f2de772be65aa9bebcb0ebf783c2e3074188804b3ac0bce92dd289c912f202110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be0307e1d475b78db1258e6b2c7e8b3cb46248f837107b62040c52aec62cdc34 0.600000000000 1454945 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": 994551, "vin": [ { "gen": { "height": 994541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be0307e1d475b78db1258e6b2c7e8b3cb46248f837107b62040c52aec62cdc34" } } ], "extra": [ 1, 227, 36, 242, 222, 119, 43, 230, 90, 169, 190, 188, 176, 235, 247, 131, 194, 227, 7, 65, 136, 128, 75, 58, 192, 188, 233, 45, 210, 137, 201, 18, 242, 2, 17, 0, 0, 0, 8, 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