Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e710e17472307ffa58fba83416330caf89522b17690530f30f3802cf960a62

Tx prefix hash: 9d0c9288e3a2712616a912eec9f2fe136af7695d4c2c83b2fe21a77e72f77419
Tx public key: d07d1bbd8c4c56f83ef70b36277fe9dee37da60c8aba540a46b61f97c87422f1
Timestamp: 1721914908 Timestamp [UCT]: 2024-07-25 13:41:48 Age [y:d:h:m:s]: 00:183:07:38:55
Block: 1073428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131108 RingCT/type: yes/0
Extra: 01d07d1bbd8c4c56f83ef70b36277fe9dee37da60c8aba540a46b61f97c87422f102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d71fb65016c0f8125a79c1e1d6e379f1b795d930c2449ec9d741045ead84d3b8 0.600000000000 1545931 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": 1073438, "vin": [ { "gen": { "height": 1073428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d71fb65016c0f8125a79c1e1d6e379f1b795d930c2449ec9d741045ead84d3b8" } } ], "extra": [ 1, 208, 125, 27, 189, 140, 76, 86, 248, 62, 247, 11, 54, 39, 127, 233, 222, 227, 125, 166, 12, 138, 186, 84, 10, 70, 182, 31, 151, 200, 116, 34, 241, 2, 17, 0, 0, 0, 4, 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