Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b705b34cb5d38a7321263270f715a8ebd87b6b33f988b5bfc9bbfa8d5fb40cb

Tx prefix hash: fb7113f1e277026491080c9ad281e663ad4a27a3b48f1956a88c8213abcaacde
Tx public key: f027749c343187a9c874302df8e412226e30cac37728eafdbf9f13551cfb6356
Timestamp: 1734303614 Timestamp [UCT]: 2024-12-15 23:00:14 Age [y:d:h:m:s]: 00:183:16:59:59
Block: 1176052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130999 RingCT/type: yes/0
Extra: 01f027749c343187a9c874302df8e412226e30cac37728eafdbf9f13551cfb63560211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a14eb0b5c9ab6e96e3b82fe32b602ce4dbee56bc26c9103e4a2fe184f537f5fa 0.600000000000 1662381 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": 1176062, "vin": [ { "gen": { "height": 1176052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a14eb0b5c9ab6e96e3b82fe32b602ce4dbee56bc26c9103e4a2fe184f537f5fa" } } ], "extra": [ 1, 240, 39, 116, 156, 52, 49, 135, 169, 200, 116, 48, 45, 248, 228, 18, 34, 110, 48, 202, 195, 119, 40, 234, 253, 191, 159, 19, 85, 28, 251, 99, 86, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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