Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 928ee1fe497f7541165aaf22643c48bd831a78a462fe910a7d71738b523c89f6

Tx prefix hash: 81ea77f2a269f063c9384ca040a5f664d6f4a1bc8f0cf92987d0a6cef4166363
Tx public key: 61329df78b63e8f966e84d2989cae2a9258edf8f7e69f5c3e775eda82fe41d55
Timestamp: 1574644400 Timestamp [UCT]: 2019-11-25 01:13:20 Age [y:d:h:m:s]: 04:358:10:30:56
Block: 16797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138148 RingCT/type: yes/0
Extra: 0161329df78b63e8f966e84d2989cae2a9258edf8f7e69f5c3e775eda82fe41d55021100000001f95225a5000000000000000000

1 output(s) for total of 539.939932313000 dcy

stealth address amount amount idx
00: cf7c1e9e1070c3d18a3281841244f8669c017e4d45f2ea51038bbb586e1cc06c 539.939932313000 23804 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": 16807, "vin": [ { "gen": { "height": 16797 } } ], "vout": [ { "amount": 539939932313, "target": { "key": "cf7c1e9e1070c3d18a3281841244f8669c017e4d45f2ea51038bbb586e1cc06c" } } ], "extra": [ 1, 97, 50, 157, 247, 139, 99, 232, 249, 102, 232, 77, 41, 137, 202, 226, 169, 37, 142, 223, 143, 126, 105, 245, 195, 231, 117, 237, 168, 47, 228, 29, 85, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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