Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc84854cf294464b3970aa08cdb1011f5cfbd39dddb08c3827ba1137dd125b91

Tx prefix hash: 3c06df9fc4c211b732e4b2465894aa86a346254432212205a22521009bc48f9a
Tx public key: 4893d8fd4df4aaf30d7a6c3479cc456aa73d3c05d925d0f2eb6e86dcbd5ffa1c
Timestamp: 1673444837 Timestamp [UCT]: 2023-01-11 13:47:17 Age [y:d:h:m:s]: 01:326:00:50:00
Block: 672456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494029 RingCT/type: yes/0
Extra: 014893d8fd4df4aaf30d7a6c3479cc456aa73d3c05d925d0f2eb6e86dcbd5ffa1c02110000000252542ceb000000000000000000

1 output(s) for total of 3.629727952000 dcy

stealth address amount amount idx
00: d7a32856bbb4c2ea47a03862695f0cb02ed561e3f6b0fa3465aeef1352076124 3.629727952000 1114003 of 0

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": 672466, "vin": [ { "gen": { "height": 672456 } } ], "vout": [ { "amount": 3629727952, "target": { "key": "d7a32856bbb4c2ea47a03862695f0cb02ed561e3f6b0fa3465aeef1352076124" } } ], "extra": [ 1, 72, 147, 216, 253, 77, 244, 170, 243, 13, 122, 108, 52, 121, 204, 69, 106, 167, 61, 60, 5, 217, 37, 208, 242, 235, 110, 134, 220, 189, 95, 250, 28, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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