Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20d4962e700b0cefe746de88b7a150b970e88e556ffbe3842b481b68ed1e1434

Tx prefix hash: dd0a70f59ed1396c342eb2e087126f73404328f6d1c4b561d0ee14ef6962b608
Tx public key: b3892e0be1af1d20b98dbf9c5d23e2132137be4f7f90ca78e3360e8c9ad11317
Timestamp: 1736988393 Timestamp [UCT]: 2025-01-16 00:46:33 Age [y:d:h:m:s]: 01:015:03:59:17
Block: 1198239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269138 RingCT/type: yes/0
Extra: 01b3892e0be1af1d20b98dbf9c5d23e2132137be4f7f90ca78e3360e8c9ad113170211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3ae891c57c2b26b307f13261e96d1543be5ecfdceb3511336d953f2c59606b8 0.600000000000 1684860 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": 1198249, "vin": [ { "gen": { "height": 1198239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3ae891c57c2b26b307f13261e96d1543be5ecfdceb3511336d953f2c59606b8" } } ], "extra": [ 1, 179, 137, 46, 11, 225, 175, 29, 32, 185, 141, 191, 156, 93, 35, 226, 19, 33, 55, 190, 79, 127, 144, 202, 120, 227, 54, 14, 140, 154, 209, 19, 23, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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