Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75264efbd08d89a58c3dc0ed65e5b1cc6b0e405cd967296752d4d3634913fc5

Tx prefix hash: 7d3031f9e114dde80f55efa1be181710e9e729efa6f4c139fe15ee02d5820a48
Tx public key: 613f6c2d32669ab5b4e596e49f6963e8ea09a2a3320c20e3754ef8a1db5da967
Timestamp: 1656993707 Timestamp [UCT]: 2022-07-05 04:01:47 Age [y:d:h:m:s]: 02:182:13:31:13
Block: 536899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651840 RingCT/type: yes/0
Extra: 01613f6c2d32669ab5b4e596e49f6963e8ea09a2a3320c20e3754ef8a1db5da96702110000000375e3f0e9000000000000000000

1 output(s) for total of 10.210120957000 dcy

stealth address amount amount idx
00: d64b3104e3b1a0ea841a85b59ef000891e5c924fa3c3346e725c1122f133f80c 10.210120957000 966712 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": 536909, "vin": [ { "gen": { "height": 536899 } } ], "vout": [ { "amount": 10210120957, "target": { "key": "d64b3104e3b1a0ea841a85b59ef000891e5c924fa3c3346e725c1122f133f80c" } } ], "extra": [ 1, 97, 63, 108, 45, 50, 102, 154, 181, 180, 229, 150, 228, 159, 105, 99, 232, 234, 9, 162, 163, 50, 12, 32, 227, 117, 78, 248, 161, 219, 93, 169, 103, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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