Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77aa5692626bedd1271c8be5ea450473010273a839358ab56cc49e3ab0383f1e

Tx prefix hash: b7d4b86b78630c4377aaf83708582bbce7da7a2a8b8ec25fd65ad2a2ebab7d45
Tx public key: fe7a13d48714de79ca3fc430f9f7f18466e8f8719e6c151c83177ef1cde84a5b
Timestamp: 1734273343 Timestamp [UCT]: 2024-12-15 14:35:43 Age [y:d:h:m:s]: 00:094:16:18:55
Block: 1175799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67447 RingCT/type: yes/0
Extra: 01fe7a13d48714de79ca3fc430f9f7f18466e8f8719e6c151c83177ef1cde84a5b0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 968af8774fdd40de50b398899dd247b8d9ed18ff0a98c2b4420a0d9c5e4bc783 0.600000000000 1662124 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": 1175809, "vin": [ { "gen": { "height": 1175799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "968af8774fdd40de50b398899dd247b8d9ed18ff0a98c2b4420a0d9c5e4bc783" } } ], "extra": [ 1, 254, 122, 19, 212, 135, 20, 222, 121, 202, 63, 196, 48, 249, 247, 241, 132, 102, 232, 248, 113, 158, 108, 21, 28, 131, 23, 126, 241, 205, 232, 74, 91, 2, 17, 0, 0, 0, 8, 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