Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e7a9a516b185a70e1511c80f8f243abb059fe4458f768b3d8d8629590c83226

Tx prefix hash: 3a5e999353b01131833fdd8803667ae9a61f05ec3df3f8c5ea1652433ed1bb48
Tx public key: 679b8f4d8d2c7f66ddb496bee336f287b8eaecb8e3111687f2797f5da8829c3a
Timestamp: 1723500636 Timestamp [UCT]: 2024-08-12 22:10:36 Age [y:d:h:m:s]: 00:131:20:32:17
Block: 1086576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94362 RingCT/type: yes/0
Extra: 01679b8f4d8d2c7f66ddb496bee336f287b8eaecb8e3111687f2797f5da8829c3a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 686c53f7d6948292965363fbe6fb248bc41a83db96e7654773d4f6c79d22bd2a 0.600000000000 1561173 of 15

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": 1086586, "vin": [ { "gen": { "height": 1086576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "686c53f7d6948292965363fbe6fb248bc41a83db96e7654773d4f6c79d22bd2a" } } ], "extra": [ 1, 103, 155, 143, 77, 141, 44, 127, 102, 221, 180, 150, 190, 227, 54, 242, 135, 184, 234, 236, 184, 227, 17, 22, 135, 242, 121, 127, 93, 168, 130, 156, 58, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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