Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e5ea6d74d9f281eb0282140eb8784f11aa7bf3303af1321873dd03dc0df18d

Tx prefix hash: 769ee748212098907d03c050c5fa18b67f4ab7f5517bc70d0415b747c1cd70b4
Tx public key: 2623467567b9f03376b76ca5e48d3bf9b65cabda32a51a1eee1d3fdcd513a322
Timestamp: 1720442717 Timestamp [UCT]: 2024-07-08 12:45:17 Age [y:d:h:m:s]: 00:274:22:45:41
Block: 1061234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196443 RingCT/type: yes/0
Extra: 012623467567b9f03376b76ca5e48d3bf9b65cabda32a51a1eee1d3fdcd513a322021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c0b885dc6be215d1a5c2219d876103abd9366339fe238f36d0a443e03db543a 0.600000000000 1531725 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": 1061244, "vin": [ { "gen": { "height": 1061234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c0b885dc6be215d1a5c2219d876103abd9366339fe238f36d0a443e03db543a" } } ], "extra": [ 1, 38, 35, 70, 117, 103, 185, 240, 51, 118, 183, 108, 165, 228, 141, 59, 249, 182, 92, 171, 218, 50, 165, 26, 30, 238, 29, 63, 220, 213, 19, 163, 34, 2, 17, 0, 0, 0, 7, 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