Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd53bfd09cb087c844bfc3de5ff80df9e8d8daca798669f8c701b83e6971fe4a

Tx prefix hash: 3b12139f6e8eb3bcbcdf0d2dc7c8c22954fa0e23db11a681bcebfa9984b9596b
Tx public key: c1833890f12eac58eecb4251cbe4bd4d7760bb9ed2a3c04804d6cc7688412968
Timestamp: 1729102860 Timestamp [UCT]: 2024-10-16 18:21:00 Age [y:d:h:m:s]: 00:042:16:10:13
Block: 1133018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30476 RingCT/type: yes/0
Extra: 01c1833890f12eac58eecb4251cbe4bd4d7760bb9ed2a3c04804d6cc768841296802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30054ff6cf4a069c724d3259abf261393251994f36eb905814b71a2aaf7c69f8 0.600000000000 1616083 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": 1133028, "vin": [ { "gen": { "height": 1133018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30054ff6cf4a069c724d3259abf261393251994f36eb905814b71a2aaf7c69f8" } } ], "extra": [ 1, 193, 131, 56, 144, 241, 46, 172, 88, 238, 203, 66, 81, 203, 228, 189, 77, 119, 96, 187, 158, 210, 163, 192, 72, 4, 214, 204, 118, 136, 65, 41, 104, 2, 17, 0, 0, 0, 2, 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