Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d00c77dccf575d314019563966fc5413ce4f4945d5d3ce30e495a31bfb73589

Tx prefix hash: 55996a01d2dace947df29ca429d340113bd623a166fcde44f19b7549a2055aee
Tx public key: ea5d8358745cd165f003e454b6c69346f7359fd3c7a13dcae58fab8953e8bc97
Timestamp: 1714019784 Timestamp [UCT]: 2024-04-25 04:36:24 Age [y:d:h:m:s]: 01:035:00:29:19
Block: 1007967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286004 RingCT/type: yes/0
Extra: 01ea5d8358745cd165f003e454b6c69346f7359fd3c7a13dcae58fab8953e8bc970211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c39a517cfe42a7f9a2b7fd3993db059aae80606cb5384d0911b209c5e37f3e49 0.600000000000 1469433 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": 1007977, "vin": [ { "gen": { "height": 1007967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c39a517cfe42a7f9a2b7fd3993db059aae80606cb5384d0911b209c5e37f3e49" } } ], "extra": [ 1, 234, 93, 131, 88, 116, 92, 209, 101, 240, 3, 228, 84, 182, 198, 147, 70, 247, 53, 159, 211, 199, 161, 61, 202, 229, 143, 171, 137, 83, 232, 188, 151, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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