Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf12ce116b17980a176a1c91456b70a24485ac08ec1631742835c5b8142aad9

Tx prefix hash: d69ed8bc735c0f6c0e5a03316381ff8312f64e000924a08b2509b3349ccac47c
Tx public key: 9020e21d223a8302ec1057eae905df7010886c38d0c8dc4dfea904e55b05c303
Timestamp: 1583750359 Timestamp [UCT]: 2020-03-09 10:39:19 Age [y:d:h:m:s]: 04:241:14:27:06
Block: 79073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067670 RingCT/type: yes/0
Extra: 019020e21d223a8302ec1057eae905df7010886c38d0c8dc4dfea904e55b05c303021100000001203e3db0000000000000000000

1 output(s) for total of 335.736932046000 dcy

stealth address amount amount idx
00: a8d66662e490893453d15a54a548a8e20a794f26a926448eb4c0c207c792d8ed 335.736932046000 144803 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": 79083, "vin": [ { "gen": { "height": 79073 } } ], "vout": [ { "amount": 335736932046, "target": { "key": "a8d66662e490893453d15a54a548a8e20a794f26a926448eb4c0c207c792d8ed" } } ], "extra": [ 1, 144, 32, 226, 29, 34, 58, 131, 2, 236, 16, 87, 234, 233, 5, 223, 112, 16, 136, 108, 56, 208, 200, 220, 77, 254, 169, 4, 229, 91, 5, 195, 3, 2, 17, 0, 0, 0, 1, 32, 62, 61, 176, 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