Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 022f8f4c2d91bce8806650a9964226118e20af3b6840dc1edc7b8efc29487e20

Tx prefix hash: 1a2b513669c3b948ad660579a87e9d9d9c43e7826b7d114e7b1a83438a63d1f7
Tx public key: c4c61e775ad3f2650c204313dc91e17292beab6d6209783cf3716c13f54393dd
Timestamp: 1694060601 Timestamp [UCT]: 2023-09-07 04:23:21 Age [y:d:h:m:s]: 01:222:04:05:29
Block: 842687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419900 RingCT/type: yes/0
Extra: 01c4c61e775ad3f2650c204313dc91e17292beab6d6209783cf3716c13f54393dd02110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.990440111000 dcy

stealth address amount amount idx
00: 19d9cd8a6477c348c0adf5ebf0472633f1bf1b21120965783ce5bea10103475f 0.990440111000 1295831 of 0

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": 842697, "vin": [ { "gen": { "height": 842687 } } ], "vout": [ { "amount": 990440111, "target": { "key": "19d9cd8a6477c348c0adf5ebf0472633f1bf1b21120965783ce5bea10103475f" } } ], "extra": [ 1, 196, 198, 30, 119, 90, 211, 242, 101, 12, 32, 67, 19, 220, 145, 225, 114, 146, 190, 171, 109, 98, 9, 120, 60, 243, 113, 108, 19, 245, 67, 147, 221, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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