Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a19e361856a697626a57612a278556c7a80cee46030f2174537158a4c68c1db

Tx prefix hash: f27eae08ea5fd3470dd140eb1a982b2eb5f7da093f221f61a3d787497e5b8ccd
Tx public key: ac0da46f4b000a68cfa1ce21311a8fe5d0d4f8a40e5ca18291be5777046d63e1
Timestamp: 1718165514 Timestamp [UCT]: 2024-06-12 04:11:54 Age [y:d:h:m:s]: 00:252:15:54:04
Block: 1042354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180497 RingCT/type: yes/0
Extra: 01ac0da46f4b000a68cfa1ce21311a8fe5d0d4f8a40e5ca18291be5777046d63e102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcd80b17bd97068f50c49ec65be5a507e40c37f3596b34222dbf8fc43b0abacc 0.600000000000 1511255 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": 1042364, "vin": [ { "gen": { "height": 1042354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcd80b17bd97068f50c49ec65be5a507e40c37f3596b34222dbf8fc43b0abacc" } } ], "extra": [ 1, 172, 13, 164, 111, 75, 0, 10, 104, 207, 161, 206, 33, 49, 26, 143, 229, 208, 212, 248, 164, 14, 92, 161, 130, 145, 190, 87, 119, 4, 109, 99, 225, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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