Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c3be1e15773979b96c45113fcc3a71756e4d7bce4c261f151e73ff25e4ae77

Tx prefix hash: 9f80fbad99af4d5a61e2b249c2b7fffaab07ec1fbe7be9ac30225536109737aa
Tx public key: f008d7f8d8f1c2effb6b8c8326df2f1359af96c37c14950e78b6bdd0b2b76b8d
Timestamp: 1702686240 Timestamp [UCT]: 2023-12-16 00:24:00 Age [y:d:h:m:s]: 01:356:09:23:35
Block: 914006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513604 RingCT/type: yes/0
Extra: 01f008d7f8d8f1c2effb6b8c8326df2f1359af96c37c14950e78b6bdd0b2b76b8d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7404e2f1fc0d8f7a8a0ca29182b12b3d73c67e663deabeeb5f9839539fd12d8 0.600000000000 1371286 of 15

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": 914016, "vin": [ { "gen": { "height": 914006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7404e2f1fc0d8f7a8a0ca29182b12b3d73c67e663deabeeb5f9839539fd12d8" } } ], "extra": [ 1, 240, 8, 215, 248, 216, 241, 194, 239, 251, 107, 140, 131, 38, 223, 47, 19, 89, 175, 150, 195, 124, 20, 149, 14, 120, 182, 189, 208, 178, 183, 107, 141, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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