Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45f526586c44aa6228f261690a2266e6cd18a2be4c9bcfa0f08f44ca4043526f

Tx prefix hash: 0d3fdc2e566670c6215054b61a81e181c2e562e3b3add27e469530ed35621434
Tx public key: ad4efae891cbc84d9cdd74379c832ab56d3cf8d232259a55674899df4905a696
Timestamp: 1574144693 Timestamp [UCT]: 2019-11-19 06:24:53 Age [y:d:h:m:s]: 05:042:04:35:54
Block: 12467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1173211 RingCT/type: yes/0
Extra: 01ad4efae891cbc84d9cdd74379c832ab56d3cf8d232259a55674899df4905a69602110000000166a80d00000000000000000000

1 output(s) for total of 558.074966126000 dcy

stealth address amount amount idx
00: 6cc53bbc84d0da742cda0d9af7e7caec14638ed95fa43d06cfe8da7a51e59f0c 558.074966126000 13788 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": 12477, "vin": [ { "gen": { "height": 12467 } } ], "vout": [ { "amount": 558074966126, "target": { "key": "6cc53bbc84d0da742cda0d9af7e7caec14638ed95fa43d06cfe8da7a51e59f0c" } } ], "extra": [ 1, 173, 78, 250, 232, 145, 203, 200, 77, 156, 221, 116, 55, 156, 131, 42, 181, 109, 60, 248, 210, 50, 37, 154, 85, 103, 72, 153, 223, 73, 5, 166, 150, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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