Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3454c284aed7c307e435be3b7bc82a9ac3707291083c63344157a37b9691bdc

Tx prefix hash: acd1aa51331670d9b6e8e1c92f76bedd3846a3549ed2f3958bafda986bf9dc91
Tx public key: 506d845e1fa83b5ab628a5a26466ba85a72e51fb633285ec0c6cff20804ea1d4
Timestamp: 1701925004 Timestamp [UCT]: 2023-12-07 04:56:44 Age [y:d:h:m:s]: 01:117:01:56:51
Block: 907700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344814 RingCT/type: yes/0
Extra: 01506d845e1fa83b5ab628a5a26466ba85a72e51fb633285ec0c6cff20804ea1d402110000000439e1d5d3000000000000000000

1 output(s) for total of 0.603132968000 dcy

stealth address amount amount idx
00: c2c0fc4d9e0ebff372a8a8c9cdace1e1a84e223f061c2438c6aa4b896bf5ae1d 0.603132968000 1364693 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": 907710, "vin": [ { "gen": { "height": 907700 } } ], "vout": [ { "amount": 603132968, "target": { "key": "c2c0fc4d9e0ebff372a8a8c9cdace1e1a84e223f061c2438c6aa4b896bf5ae1d" } } ], "extra": [ 1, 80, 109, 132, 94, 31, 168, 59, 90, 182, 40, 165, 162, 100, 102, 186, 133, 167, 46, 81, 251, 99, 50, 133, 236, 12, 108, 255, 32, 128, 78, 161, 212, 2, 17, 0, 0, 0, 4, 57, 225, 213, 211, 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