Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b1807061b69d02eb3e3716fab2ef8acb8529a18c2f41910531112d78551a659

Tx prefix hash: 3842fcfa1a4601aac21f7b7b68b6e53c85cac85d967379d661680f8a1aa00a39
Tx public key: 804a025886c28f829581f4ded26384b51ba81187b4ea3077b6df4ee0819ada44
Timestamp: 1715147042 Timestamp [UCT]: 2024-05-08 05:44:02 Age [y:d:h:m:s]: 00:204:09:07:57
Block: 1017330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146300 RingCT/type: yes/0
Extra: 01804a025886c28f829581f4ded26384b51ba81187b4ea3077b6df4ee0819ada440211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 258cb5c39cb2559d91036e5f5d19b33671a4e0c3cb6153827692a75e7462d1d2 0.600000000000 1481103 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": 1017340, "vin": [ { "gen": { "height": 1017330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "258cb5c39cb2559d91036e5f5d19b33671a4e0c3cb6153827692a75e7462d1d2" } } ], "extra": [ 1, 128, 74, 2, 88, 134, 194, 143, 130, 149, 129, 244, 222, 210, 99, 132, 181, 27, 168, 17, 135, 180, 234, 48, 119, 182, 223, 78, 224, 129, 154, 218, 68, 2, 17, 0, 0, 0, 5, 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