Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8dbb396ce3720e3dac1dbf252537f0abd1e4187be3ee7ceb356d100cae5ed4

Tx prefix hash: 1a8e115ed1db5979a51e8f4b5c22f7e36cf4dd69e1c4891b77a0e8cc1d2c9d40
Tx public key: 2020c74922b28faa9ee97439801c5b7e71df265390d9c9ff844d7fa5fbd5e4fd
Timestamp: 1680991634 Timestamp [UCT]: 2023-04-08 22:07:14 Age [y:d:h:m:s]: 02:009:23:56:41
Block: 734452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529244 RingCT/type: yes/0
Extra: 012020c74922b28faa9ee97439801c5b7e71df265390d9c9ff844d7fa5fbd5e4fd021100000005b3164c24000000000000000000

1 output(s) for total of 2.261808670000 dcy

stealth address amount amount idx
00: b918a773ffc6851b99bc4f3676bc778045ade0f590a3a3b7dc5b44c7f884f3f5 2.261808670000 1180659 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": 734462, "vin": [ { "gen": { "height": 734452 } } ], "vout": [ { "amount": 2261808670, "target": { "key": "b918a773ffc6851b99bc4f3676bc778045ade0f590a3a3b7dc5b44c7f884f3f5" } } ], "extra": [ 1, 32, 32, 199, 73, 34, 178, 143, 170, 158, 233, 116, 57, 128, 28, 91, 126, 113, 223, 38, 83, 144, 217, 201, 255, 132, 77, 127, 165, 251, 213, 228, 253, 2, 17, 0, 0, 0, 5, 179, 22, 76, 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