Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 150cbc3dd36eeb45b415ef40bd994eee9d1e13d99635715e3eb08b1adb619b21

Tx prefix hash: 8a0bde519fe9c471927014991ca4566737b97bd83587c7f1f09b440cfbc81c5d
Tx public key: 51d4f4186e5e7f982ee428a920d4132c647ed75ab3aecf37f322afa75c8d0a9a
Timestamp: 1707438664 Timestamp [UCT]: 2024-02-09 00:31:04 Age [y:d:h:m:s]: 01:122:06:44:26
Block: 953406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348502 RingCT/type: yes/0
Extra: 0151d4f4186e5e7f982ee428a920d4132c647ed75ab3aecf37f322afa75c8d0a9a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9bdf174f9de3e85be078a14cb3db674eac9a6294163cd843fae153815aeba28 0.600000000000 1412608 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": 953416, "vin": [ { "gen": { "height": 953406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9bdf174f9de3e85be078a14cb3db674eac9a6294163cd843fae153815aeba28" } } ], "extra": [ 1, 81, 212, 244, 24, 110, 94, 127, 152, 46, 228, 40, 169, 32, 212, 19, 44, 100, 126, 215, 90, 179, 174, 207, 55, 243, 34, 175, 167, 92, 141, 10, 154, 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