Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705b0dbb8efda1db9fcb5a9fb7743874cd6b405c6558ddab64d51b73635e0079

Tx prefix hash: 5297f03e0aeec9fa173a5b8e2dc8b898f756a257a381857378c377035192df25
Tx public key: 098d70632f32e4c2615ba3b922ccc22afdcd8639ecc43c72c1d1ee46f00526ae
Timestamp: 1707234597 Timestamp [UCT]: 2024-02-06 15:49:57 Age [y:d:h:m:s]: 01:271:18:19:03
Block: 951711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453000 RingCT/type: yes/0
Extra: 01098d70632f32e4c2615ba3b922ccc22afdcd8639ecc43c72c1d1ee46f00526ae02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 268fbdc0d095a16a48c533813caec9fb72d385e797f4ae624e900abbf6e15326 0.600000000000 1410517 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": 951721, "vin": [ { "gen": { "height": 951711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "268fbdc0d095a16a48c533813caec9fb72d385e797f4ae624e900abbf6e15326" } } ], "extra": [ 1, 9, 141, 112, 99, 47, 50, 228, 194, 97, 91, 163, 185, 34, 204, 194, 42, 253, 205, 134, 57, 236, 196, 60, 114, 193, 209, 238, 70, 240, 5, 38, 174, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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