Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93095e59ec7a442ada654eb8a1793b4665e0d1e316973ab3d6b5d164b6878437

Tx prefix hash: 66afaaa0313d7c4c329ce364858af2c956918756e6cc7126c730a548615c9aa0
Tx public key: 2312e4957e0fc68d1efb05fdb6cca89129c5af48f8ecc9c9afa32178dc4fe1c0
Timestamp: 1702394426 Timestamp [UCT]: 2023-12-12 15:20:26 Age [y:d:h:m:s]: 01:141:12:46:07
Block: 911614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362291 RingCT/type: yes/0
Extra: 012312e4957e0fc68d1efb05fdb6cca89129c5af48f8ecc9c9afa32178dc4fe1c002110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4efcd521d273eed86ce02514f90cdd544e8ddbbfc94612dff204da47edefb6a9 0.600000000000 1368828 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": 911624, "vin": [ { "gen": { "height": 911614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4efcd521d273eed86ce02514f90cdd544e8ddbbfc94612dff204da47edefb6a9" } } ], "extra": [ 1, 35, 18, 228, 149, 126, 15, 198, 141, 30, 251, 5, 253, 182, 204, 168, 145, 41, 197, 175, 72, 248, 236, 201, 201, 175, 163, 33, 120, 220, 79, 225, 192, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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