Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7762694c999032467f0f1c7e90c30d684f8da174a25f43d956ead7c36ad99087

Tx prefix hash: 3379ca65de0015ae3402014eef3bbd2bed2da347e8fbfa81ddd3eb17aad3c621
Tx public key: eb0d20b9dfbce710cdd4b4e7aae5eb44009ed117be7b38c5c32279e1727851f5
Timestamp: 1733654745 Timestamp [UCT]: 2024-12-08 10:45:45 Age [y:d:h:m:s]: 00:192:06:26:59
Block: 1170667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137125 RingCT/type: yes/0
Extra: 01eb0d20b9dfbce710cdd4b4e7aae5eb44009ed117be7b38c5c32279e1727851f502110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 304c21d520b8b1a91367c7a3978156786a05a7572caafc196abe5e45df966e5d 0.600000000000 1656398 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": 1170677, "vin": [ { "gen": { "height": 1170667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "304c21d520b8b1a91367c7a3978156786a05a7572caafc196abe5e45df966e5d" } } ], "extra": [ 1, 235, 13, 32, 185, 223, 188, 231, 16, 205, 212, 180, 231, 170, 229, 235, 68, 0, 158, 209, 23, 190, 123, 56, 197, 195, 34, 121, 225, 114, 120, 81, 245, 2, 17, 0, 0, 0, 15, 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