Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438d5c1092da73b5aecc3fac41284ce8a80678d05a20c20e93a2d307723ea434

Tx prefix hash: 022af0f9012ca4580d40710d8dd3c01615fef25b118cc8804a68be714583da84
Tx public key: af48b130b77309fe8f23424a30e96f853114ca1c676d5583460cb11b56c11b6a
Timestamp: 1659659186 Timestamp [UCT]: 2022-08-05 00:26:26 Age [y:d:h:m:s]: 02:284:08:50:18
Block: 558886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724472 RingCT/type: yes/0
Extra: 01af48b130b77309fe8f23424a30e96f853114ca1c676d5583460cb11b56c11b6a021100000002eae24e24000000000000000000

1 output(s) for total of 8.633339044000 dcy

stealth address amount amount idx
00: 16f38083068ff5c77cd94c5b3c738ced65a9a0d3b1791a1e1e56528bc0d2d2a5 8.633339044000 990992 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": 558896, "vin": [ { "gen": { "height": 558886 } } ], "vout": [ { "amount": 8633339044, "target": { "key": "16f38083068ff5c77cd94c5b3c738ced65a9a0d3b1791a1e1e56528bc0d2d2a5" } } ], "extra": [ 1, 175, 72, 177, 48, 183, 115, 9, 254, 143, 35, 66, 74, 48, 233, 111, 133, 49, 20, 202, 28, 103, 109, 85, 131, 70, 12, 177, 27, 86, 193, 27, 106, 2, 17, 0, 0, 0, 2, 234, 226, 78, 36, 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