Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5395a3a0a41801764a2d1dc070bdb5ff7866e0b746cccde3fe5a0de88166d337

Tx prefix hash: 4cf754288aefeec9bc5c925c9741c21abcbdf18bbac93c475cfe2144ec0dfa25
Tx public key: 841437815b48cf05c56aee545555d3c73fe16f6ea1bc09528b1660b61756e5b4
Timestamp: 1706171478 Timestamp [UCT]: 2024-01-25 08:31:18 Age [y:d:h:m:s]: 01:137:10:26:37
Block: 942879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359371 RingCT/type: yes/0
Extra: 01841437815b48cf05c56aee545555d3c73fe16f6ea1bc09528b1660b61756e5b402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71093c02813aed3d58dd8aa6295f363f24fc41ac4b5a7f3ec39c78376e6205cd 0.600000000000 1401059 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": 942889, "vin": [ { "gen": { "height": 942879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71093c02813aed3d58dd8aa6295f363f24fc41ac4b5a7f3ec39c78376e6205cd" } } ], "extra": [ 1, 132, 20, 55, 129, 91, 72, 207, 5, 197, 106, 238, 84, 85, 85, 211, 199, 63, 225, 111, 110, 161, 188, 9, 82, 139, 22, 96, 182, 23, 86, 229, 180, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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