Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41859a632d9c5745801a5c43663397fb0e93aae2a2e44a34d32897b2bdbc5e61

Tx prefix hash: 7027dee31859d45b70cdcc561f170eac44debe3dc97e40843ce73b2714f6152d
Tx public key: 6e795d28a65ea693a364dbe041d14ebfbb6f337716a9340b76897ba907e2d17e
Timestamp: 1703708110 Timestamp [UCT]: 2023-12-27 20:15:10 Age [y:d:h:m:s]: 01:113:14:41:33
Block: 922485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342313 RingCT/type: yes/0
Extra: 016e795d28a65ea693a364dbe041d14ebfbb6f337716a9340b76897ba907e2d17e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435d96063e26b8050908a8f906d596b59151a81cd868a9e8b95d87e6f3061ba2 0.600000000000 1380183 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": 922495, "vin": [ { "gen": { "height": 922485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435d96063e26b8050908a8f906d596b59151a81cd868a9e8b95d87e6f3061ba2" } } ], "extra": [ 1, 110, 121, 93, 40, 166, 94, 166, 147, 163, 100, 219, 224, 65, 209, 78, 191, 187, 111, 51, 119, 22, 169, 52, 11, 118, 137, 123, 169, 7, 226, 209, 126, 2, 17, 0, 0, 0, 1, 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