Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ce4509e3c8eeb093a2c79ecedf859d8bf620ddd9658366a8f1ffdc9ab6f6fc

Tx prefix hash: 85605b86c845def88b2ca6a8e8b9896f1b8a5a4dc9c77a9f3c797ba344a84a14
Tx public key: bfcb44fbfd2f1fae3544672c5dfc4ea2518f353987c2ef0f262629f2847d7d5a
Timestamp: 1710838753 Timestamp [UCT]: 2024-03-19 08:59:13 Age [y:d:h:m:s]: 00:309:18:23:45
Block: 981627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221668 RingCT/type: yes/0
Extra: 01bfcb44fbfd2f1fae3544672c5dfc4ea2518f353987c2ef0f262629f2847d7d5a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 059b7af38ac2a41bdaf0386caf8450594197f373d98c9b9311f9c96adce9c2a1 0.600000000000 1441724 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": 981637, "vin": [ { "gen": { "height": 981627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "059b7af38ac2a41bdaf0386caf8450594197f373d98c9b9311f9c96adce9c2a1" } } ], "extra": [ 1, 191, 203, 68, 251, 253, 47, 31, 174, 53, 68, 103, 44, 93, 252, 78, 162, 81, 143, 53, 57, 135, 194, 239, 15, 38, 38, 41, 242, 132, 125, 125, 90, 2, 17, 0, 0, 0, 2, 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