Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389fdcc6ac6ba2c55a3864ef9ff2f5d71e5961b91b7a5b9561b0381b96f388eb

Tx prefix hash: aad87380303140af1c0f30f882a426f1cc02d8cf23e200e9073613428a70795d
Tx public key: f7da7e5f3da0ace9c1c7e0aec742b2ea2c382f2c11acd361e3f7bdf9f7bef3a5
Timestamp: 1721922252 Timestamp [UCT]: 2024-07-25 15:44:12 Age [y:d:h:m:s]: 00:265:23:00:00
Block: 1073489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189989 RingCT/type: yes/0
Extra: 01f7da7e5f3da0ace9c1c7e0aec742b2ea2c382f2c11acd361e3f7bdf9f7bef3a5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 279a347cb9f73c297c9ca0be36ace40add85e49c8f4538fb64f8957f12a610b4 0.600000000000 1545992 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": 1073499, "vin": [ { "gen": { "height": 1073489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "279a347cb9f73c297c9ca0be36ace40add85e49c8f4538fb64f8957f12a610b4" } } ], "extra": [ 1, 247, 218, 126, 95, 61, 160, 172, 233, 193, 199, 224, 174, 199, 66, 178, 234, 44, 56, 47, 44, 17, 172, 211, 97, 227, 247, 189, 249, 247, 190, 243, 165, 2, 17, 0, 0, 0, 3, 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