Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9552836f38ab8a09eebd7da3370a7d91c6106521c5ca36c7c863f9a950a0461

Tx prefix hash: e5250073736813b8647bdde4e3aba0ced888570e3555f10cb412ea733afcc0ca
Tx public key: 5bdc76f42c951450c9cc071f4f9cad51753a47aea47d4cdcbe1fdf397a2304d4
Timestamp: 1738862926 Timestamp [UCT]: 2025-02-06 17:28:46 Age [y:d:h:m:s]: 00:287:04:20:31
Block: 1213510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203002 RingCT/type: yes/0
Extra: 015bdc76f42c951450c9cc071f4f9cad51753a47aea47d4cdcbe1fdf397a2304d4021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a5da9c5bb9b598b007dd2c855a4c0642a8e2c113c9161ce6d17b34b9888eaaa 0.600000000000 1700289 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": 1213520, "vin": [ { "gen": { "height": 1213510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a5da9c5bb9b598b007dd2c855a4c0642a8e2c113c9161ce6d17b34b9888eaaa" } } ], "extra": [ 1, 91, 220, 118, 244, 44, 149, 20, 80, 201, 204, 7, 31, 79, 156, 173, 81, 117, 58, 71, 174, 164, 125, 76, 220, 190, 31, 223, 57, 122, 35, 4, 212, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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