Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4bc21e34261944a4fcd732673b3f539b738918a9d15dfb0999405301f3e2da6

Tx prefix hash: b297b35d4c13c716a10fe8854f255b77f2a8f6b8edcebe401684b96a1ccd9106
Tx public key: 8196d9787445895078c71f08b25a265324e8d6e86c753518456a0d6b6971f57b
Timestamp: 1717370557 Timestamp [UCT]: 2024-06-02 23:22:37 Age [y:d:h:m:s]: 00:310:21:00:48
Block: 1035770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222154 RingCT/type: yes/0
Extra: 018196d9787445895078c71f08b25a265324e8d6e86c753518456a0d6b6971f57b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54ff4b449b0998ca68bbe5105afd2e8f1f6ec0c9c74a90b96c0427d84804f8d2 0.600000000000 1504293 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": 1035780, "vin": [ { "gen": { "height": 1035770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54ff4b449b0998ca68bbe5105afd2e8f1f6ec0c9c74a90b96c0427d84804f8d2" } } ], "extra": [ 1, 129, 150, 217, 120, 116, 69, 137, 80, 120, 199, 31, 8, 178, 90, 38, 83, 36, 232, 214, 232, 108, 117, 53, 24, 69, 106, 13, 107, 105, 113, 245, 123, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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