Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 470d8fc6e135c7f48c7cb6664f4446119d03b44b8069c70bef10ded60a4bda8d

Tx prefix hash: 54a9c414a41fc65a5a9c77226035d6f6f7d45c17ec942bdba37fb79cdd7e49ed
Tx public key: 27d31c54d207bfce35cc64de84329e52a01de116bc18696efec300fdc7be3885
Timestamp: 1577646197 Timestamp [UCT]: 2019-12-29 19:03:17 Age [y:d:h:m:s]: 05:307:20:24:40
Block: 34496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367515 RingCT/type: yes/0
Extra: 0127d31c54d207bfce35cc64de84329e52a01de116bc18696efec300fdc7be3885021100000013d81c26c0000000000000000000

1 output(s) for total of 471.738463018000 dcy

stealth address amount amount idx
00: bcc1dbaf84c89d043876e28f97d745e61c0c61c7daf8331a32865577f2f9e7e2 471.738463018000 58062 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": 34506, "vin": [ { "gen": { "height": 34496 } } ], "vout": [ { "amount": 471738463018, "target": { "key": "bcc1dbaf84c89d043876e28f97d745e61c0c61c7daf8331a32865577f2f9e7e2" } } ], "extra": [ 1, 39, 211, 28, 84, 210, 7, 191, 206, 53, 204, 100, 222, 132, 50, 158, 82, 160, 29, 225, 22, 188, 24, 105, 110, 254, 195, 0, 253, 199, 190, 56, 133, 2, 17, 0, 0, 0, 19, 216, 28, 38, 192, 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