Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19ec81c7b031a39160d803c011544a51fd9113d5d48a0d3bde2fabd1019a4e65

Tx prefix hash: 4d867d7ea80090232e0b3129ce77ed313cf765ac1956a41b31e49452a9e852db
Tx public key: d895e24e05f6f0f4f59effdf57059d672bcfe50bb8985ef4a31e4a122a45a5eb
Timestamp: 1707630588 Timestamp [UCT]: 2024-02-11 05:49:48 Age [y:d:h:m:s]: 01:267:00:25:54
Block: 954995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449605 RingCT/type: yes/0
Extra: 01d895e24e05f6f0f4f59effdf57059d672bcfe50bb8985ef4a31e4a122a45a5eb0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538c296b0b04e257aa39687a021fb6687699fd44cdbd6828dbb60ae70e22d229 0.600000000000 1414277 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": 955005, "vin": [ { "gen": { "height": 954995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538c296b0b04e257aa39687a021fb6687699fd44cdbd6828dbb60ae70e22d229" } } ], "extra": [ 1, 216, 149, 226, 78, 5, 246, 240, 244, 245, 158, 255, 223, 87, 5, 157, 103, 43, 207, 229, 11, 184, 152, 94, 244, 163, 30, 74, 18, 42, 69, 165, 235, 2, 17, 0, 0, 0, 8, 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