Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9651e49c1868d1568f8f7d901fbf4070240a5d2cdf9d0c4628f0e7fc3e2909e

Tx prefix hash: e0660f5918fc73fc41361a4d3b07a6cbda3122fb097787b2ef63a519e061b496
Tx public key: 990ac9577559d62d5689b4e05eccd5884defd223e4c64a415b45f46efdb01e3f
Timestamp: 1728215207 Timestamp [UCT]: 2024-10-06 11:46:47 Age [y:d:h:m:s]: 00:112:03:01:57
Block: 1125666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80110 RingCT/type: yes/0
Extra: 01990ac9577559d62d5689b4e05eccd5884defd223e4c64a415b45f46efdb01e3f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6c6ffcbc5a57ff21a98dd59cab2e63a49f51d36368373a7c65f11eed4067223 0.600000000000 1608417 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": 1125676, "vin": [ { "gen": { "height": 1125666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c6ffcbc5a57ff21a98dd59cab2e63a49f51d36368373a7c65f11eed4067223" } } ], "extra": [ 1, 153, 10, 201, 87, 117, 89, 214, 45, 86, 137, 180, 224, 94, 204, 213, 136, 77, 239, 210, 35, 228, 198, 74, 65, 91, 69, 244, 110, 253, 176, 30, 63, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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