Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc7966923a64d403e176fe2c24c47ba47fab87ee03c26ab0a4a81b0e53c4e71c

Tx prefix hash: 38a441980add22f78a6538865e86037ae55b2c07bbf3323bb6bd0ac4581b31e3
Tx public key: 40d437f198f44338a9978caa69874a8eef54c8538a6cf8b971742c5393bddce6
Timestamp: 1578480826 Timestamp [UCT]: 2020-01-08 10:53:46 Age [y:d:h:m:s]: 04:302:14:50:08
Block: 41146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105616 RingCT/type: yes/0
Extra: 0140d437f198f44338a9978caa69874a8eef54c8538a6cf8b971742c5393bddce602110000000a8a2ee0d9000000000000000000

1 output(s) for total of 448.401511051000 dcy

stealth address amount amount idx
00: 37d389e57fecb2f4d0fa244ff88ce8824a78128f39657af58ed8c16635cc0cdf 448.401511051000 73026 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": 41156, "vin": [ { "gen": { "height": 41146 } } ], "vout": [ { "amount": 448401511051, "target": { "key": "37d389e57fecb2f4d0fa244ff88ce8824a78128f39657af58ed8c16635cc0cdf" } } ], "extra": [ 1, 64, 212, 55, 241, 152, 244, 67, 56, 169, 151, 140, 170, 105, 135, 74, 142, 239, 84, 200, 83, 138, 108, 248, 185, 113, 116, 44, 83, 147, 189, 220, 230, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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