Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88cd11a604c184153e6197c55a3dd5c87ac02016c917f040bbdcb1c28a7eb381

Tx prefix hash: b44059a21d807a98c4cd8b9e8b9a56be0bf4e0e464c51512e08d4779a9ace1c7
Tx public key: 9466752289a3d93262ab329e8d19d779ca1b57f35952dd4bad27b691b1c3d224
Timestamp: 1723957411 Timestamp [UCT]: 2024-08-18 05:03:31 Age [y:d:h:m:s]: 01:080:22:37:18
Block: 1090374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316291 RingCT/type: yes/0
Extra: 019466752289a3d93262ab329e8d19d779ca1b57f35952dd4bad27b691b1c3d224021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb3c9a2f5c31aca946ac2ee96155288ee2bbc267e82529b50da020892899a22 0.600000000000 1564997 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": 1090384, "vin": [ { "gen": { "height": 1090374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb3c9a2f5c31aca946ac2ee96155288ee2bbc267e82529b50da020892899a22" } } ], "extra": [ 1, 148, 102, 117, 34, 137, 163, 217, 50, 98, 171, 50, 158, 141, 25, 215, 121, 202, 27, 87, 243, 89, 82, 221, 75, 173, 39, 182, 145, 177, 195, 210, 36, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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