Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a107388a72d4435efb6e58431616f907cc9fa22d56dbe4ff308310dbc45184fe

Tx prefix hash: c4e70675408f826fd4f19cc1585e93258ec0b03fd75231db1bed12d88d02c426
Tx public key: 305c7ef70441e3f0c9d8d56a18592fd4a851e71c775c55d9ba55c194bfab859d
Timestamp: 1709842198 Timestamp [UCT]: 2024-03-07 20:09:58 Age [y:d:h:m:s]: 01:069:04:36:26
Block: 973349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310464 RingCT/type: yes/0
Extra: 01305c7ef70441e3f0c9d8d56a18592fd4a851e71c775c55d9ba55c194bfab859d02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fe871fe28df2f8f0cc02385c7f0eff24b420e5f647565451b7830877a75ef10 0.600000000000 1433284 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": 973359, "vin": [ { "gen": { "height": 973349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fe871fe28df2f8f0cc02385c7f0eff24b420e5f647565451b7830877a75ef10" } } ], "extra": [ 1, 48, 92, 126, 247, 4, 65, 227, 240, 201, 216, 213, 106, 24, 89, 47, 212, 168, 81, 231, 28, 119, 92, 85, 217, 186, 85, 193, 148, 191, 171, 133, 157, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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