Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af3b960f48087dada8e476fbfd36ef6f2497ae1ff700ac51ff4d64c6681044f6

Tx prefix hash: cf4b8257dcf9d9a56168bf6bc2102238a2cda1c1a4ec0bc018874023dd9d6432
Tx public key: bb4db6d419d955e6c4e4553c5d358dad603a27e590c2b350c92071d71efb6eaf
Timestamp: 1579790196 Timestamp [UCT]: 2020-01-23 14:36:36 Age [y:d:h:m:s]: 05:286:14:59:09
Block: 51238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1353340 RingCT/type: yes/0
Extra: 01bb4db6d419d955e6c4e4553c5d358dad603a27e590c2b350c92071d71efb6eaf021100000001d81c26c0000000000000000000

1 output(s) for total of 415.172010603000 dcy

stealth address amount amount idx
00: 197e46593ced18c6bda25aea02e26c91e859bc134ccfa854c1184dc1cede5700 415.172010603000 95115 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": 51248, "vin": [ { "gen": { "height": 51238 } } ], "vout": [ { "amount": 415172010603, "target": { "key": "197e46593ced18c6bda25aea02e26c91e859bc134ccfa854c1184dc1cede5700" } } ], "extra": [ 1, 187, 77, 182, 212, 25, 217, 85, 230, 196, 228, 85, 60, 93, 53, 141, 173, 96, 58, 39, 229, 144, 194, 179, 80, 201, 32, 113, 215, 30, 251, 110, 175, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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