Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24345094f00b85d64a4727fe9677ba716f4b41adbcd43b704240800cc7d3439a

Tx prefix hash: 2661b0f2a31f5b12c3b54619a5a8331709315ac4f9c8a9c922c3d2aabc607b87
Tx public key: 5a3a966dbd5c46d6d611e974c258136f24d47320713077d1cc144a7a7aa8dba0
Timestamp: 1578928814 Timestamp [UCT]: 2020-01-13 15:20:14 Age [y:d:h:m:s]: 04:349:22:43:24
Block: 44755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139586 RingCT/type: yes/0
Extra: 015a3a966dbd5c46d6d611e974c258136f24d47320713077d1cc144a7a7aa8dba002110000000b4ac5aa02000000000000000000

1 output(s) for total of 436.306978536000 dcy

stealth address amount amount idx
00: b26c8509041a344781d95ed6c9ca8ac8b6897df44049a961008c61c69a333f17 436.306978536000 81519 of 0

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": 44765, "vin": [ { "gen": { "height": 44755 } } ], "vout": [ { "amount": 436306978536, "target": { "key": "b26c8509041a344781d95ed6c9ca8ac8b6897df44049a961008c61c69a333f17" } } ], "extra": [ 1, 90, 58, 150, 109, 189, 92, 70, 214, 214, 17, 233, 116, 194, 88, 19, 111, 36, 212, 115, 32, 113, 48, 119, 209, 204, 20, 74, 122, 122, 168, 219, 160, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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