Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 149f1768830535411a6b66608d09297e45600b59a58cb02ce8ecc687f07e5b74

Tx prefix hash: 04365f4d1d5c7762d365170d32977f8065631ec533eb04a220de95b4dfed11bb
Tx public key: 75a820cab8ec5f5c4ddc19a8d8948fe4ece969f5ce171c8c1da52a61b3c3b978
Timestamp: 1736761666 Timestamp [UCT]: 2025-01-13 09:47:46 Age [y:d:h:m:s]: 00:063:21:58:00
Block: 1196383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45447 RingCT/type: yes/0
Extra: 0175a820cab8ec5f5c4ddc19a8d8948fe4ece969f5ce171c8c1da52a61b3c3b978021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e35930adee5d1c8daf04d1aeac6df781b97eb10cec790db516b523bfda6ede1 0.600000000000 1682982 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": 1196393, "vin": [ { "gen": { "height": 1196383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e35930adee5d1c8daf04d1aeac6df781b97eb10cec790db516b523bfda6ede1" } } ], "extra": [ 1, 117, 168, 32, 202, 184, 236, 95, 92, 77, 220, 25, 168, 216, 148, 143, 228, 236, 233, 105, 245, 206, 23, 28, 140, 29, 165, 42, 97, 179, 195, 185, 120, 2, 17, 0, 0, 0, 1, 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