Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c62d93c645d42704d589bd888827e9e19140717b040dce1df913d9e7b995ce

Tx prefix hash: 4d424e6f0f7601fccd22b23346ed803e33f89a78409cc88463c5158fdd90b4be
Tx public key: c6a3bf15c42f50a70f95dfe8b45dd9efda9a1cac57bec0da46324f996bc2e9e8
Timestamp: 1722724917 Timestamp [UCT]: 2024-08-03 22:41:57 Age [y:d:h:m:s]: 00:249:12:02:44
Block: 1080144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178221 RingCT/type: yes/0
Extra: 01c6a3bf15c42f50a70f95dfe8b45dd9efda9a1cac57bec0da46324f996bc2e9e8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 382a172955561543591c3ae2bfe55a29819f058c5bc72b9ea96cd759e13aee7e 0.600000000000 1553393 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": 1080154, "vin": [ { "gen": { "height": 1080144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "382a172955561543591c3ae2bfe55a29819f058c5bc72b9ea96cd759e13aee7e" } } ], "extra": [ 1, 198, 163, 191, 21, 196, 47, 80, 167, 15, 149, 223, 232, 180, 93, 217, 239, 218, 154, 28, 172, 87, 190, 192, 218, 70, 50, 79, 153, 107, 194, 233, 232, 2, 17, 0, 0, 0, 2, 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