Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0638e108c089cf73f179814a74b7c203138af502fc94d3caa3e3adba5e9e4c

Tx prefix hash: edf0df0a2cf52fec39689117f3b8f26f4eea655191f30717d9e790691dfc9e46
Tx public key: 7cd3b025b710ca208d33e1b3f6c1b80f3b1a887c2fc6a2f937c9afa92a715be9
Timestamp: 1722745332 Timestamp [UCT]: 2024-08-04 04:22:12 Age [y:d:h:m:s]: 00:296:14:40:46
Block: 1080316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211915 RingCT/type: yes/0
Extra: 017cd3b025b710ca208d33e1b3f6c1b80f3b1a887c2fc6a2f937c9afa92a715be902110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9779aaca0dac396ba971876b72d91603a49acca77f75026a977344c1bc4909e2 0.600000000000 1553619 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": 1080326, "vin": [ { "gen": { "height": 1080316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9779aaca0dac396ba971876b72d91603a49acca77f75026a977344c1bc4909e2" } } ], "extra": [ 1, 124, 211, 176, 37, 183, 16, 202, 32, 141, 51, 225, 179, 246, 193, 184, 15, 59, 26, 136, 124, 47, 198, 162, 249, 55, 201, 175, 169, 42, 113, 91, 233, 2, 17, 0, 0, 0, 12, 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