Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b2689719a1457e408f1350146c3879aea4b8bfd1b61f93168101c80c032737d

Tx prefix hash: 998ed58586f7b2c4056a81b6d02bba715b83ca3aee57f5de66270ab27a3198a6
Tx public key: e5cc26ae05fb967e533cb0ef54390b1f7bb28efe4b4f238dfa2e16aba2ec8327
Timestamp: 1725431636 Timestamp [UCT]: 2024-09-04 06:33:56 Age [y:d:h:m:s]: 00:242:09:45:06
Block: 1102589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173107 RingCT/type: yes/0
Extra: 01e5cc26ae05fb967e533cb0ef54390b1f7bb28efe4b4f238dfa2e16aba2ec8327021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5855a743da0f1508ecb10335216739ad908a85622131ffb23ef726d824b0d992 0.600000000000 1579084 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": 1102599, "vin": [ { "gen": { "height": 1102589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5855a743da0f1508ecb10335216739ad908a85622131ffb23ef726d824b0d992" } } ], "extra": [ 1, 229, 204, 38, 174, 5, 251, 150, 126, 83, 60, 176, 239, 84, 57, 11, 31, 123, 178, 142, 254, 75, 79, 35, 141, 250, 46, 22, 171, 162, 236, 131, 39, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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