Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b054844675917237c731c05123beae699f8521399c3918317f73407e9fd66933

Tx prefix hash: e4ee89e2d6144f409ae2bea171d0c16e513fe8c3a48b95765724276bbfd29e13
Tx public key: c9dc47feb21944ee50de5a643d33495f1a551fac39efc7b7196e8c9db5266404
Timestamp: 1645461820 Timestamp [UCT]: 2022-02-21 16:43:40 Age [y:d:h:m:s]: 03:021:14:01:34
Block: 443464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795485 RingCT/type: yes/0
Extra: 01c9dc47feb21944ee50de5a643d33495f1a551fac39efc7b7196e8c9db52664040211000000055eb576c5000000000000000000

1 output(s) for total of 20.826676235000 dcy

stealth address amount amount idx
00: 841fb899f7499153ae6934029cdfd2ac4ef956c510fd4fc295edeecb7b1d032e 20.826676235000 856503 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": 443474, "vin": [ { "gen": { "height": 443464 } } ], "vout": [ { "amount": 20826676235, "target": { "key": "841fb899f7499153ae6934029cdfd2ac4ef956c510fd4fc295edeecb7b1d032e" } } ], "extra": [ 1, 201, 220, 71, 254, 178, 25, 68, 238, 80, 222, 90, 100, 61, 51, 73, 95, 26, 85, 31, 172, 57, 239, 199, 183, 25, 110, 140, 157, 181, 38, 100, 4, 2, 17, 0, 0, 0, 5, 94, 181, 118, 197, 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