Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7202da9d192951f3cfb1ceeed9361de5a8a34dfb832a74103a88da46a1f43d8

Tx prefix hash: 6ba741a561bd92d38a1c6eb9d3d20040a17bb2875d1362dbeffdaae737705a6d
Tx public key: 45b99f9f4e11dab6611219527d4e78e972d0c1f5e712f22839c5613d2452e0d2
Timestamp: 1721542491 Timestamp [UCT]: 2024-07-21 06:14:51 Age [y:d:h:m:s]: 00:127:00:25:53
Block: 1070331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90895 RingCT/type: yes/0
Extra: 0145b99f9f4e11dab6611219527d4e78e972d0c1f5e712f22839c5613d2452e0d202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 926128eb7e4dc236e7f01087be010f70c5664629ff42a40de896ffc13ee73e90 0.600000000000 1542122 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": 1070341, "vin": [ { "gen": { "height": 1070331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "926128eb7e4dc236e7f01087be010f70c5664629ff42a40de896ffc13ee73e90" } } ], "extra": [ 1, 69, 185, 159, 159, 78, 17, 218, 182, 97, 18, 25, 82, 125, 78, 120, 233, 114, 208, 193, 245, 231, 18, 242, 40, 57, 197, 97, 61, 36, 82, 224, 210, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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