Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff1947712577f66ce1f9a26f35fd9c828ba9ec15b8bc5e4181941deb263b863f

Tx prefix hash: 150ed0d31cb9accd6f169d71e6edf750f473a0ee760d72fcf8d56118907e7c12
Tx public key: e10b1fad3c615184a07095cf2baee1a0b97e594cec25e42491fcf82adba8d97c
Timestamp: 1702585265 Timestamp [UCT]: 2023-12-14 20:21:05 Age [y:d:h:m:s]: 00:282:02:30:02
Block: 913171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202079 RingCT/type: yes/0
Extra: 01e10b1fad3c615184a07095cf2baee1a0b97e594cec25e42491fcf82adba8d97c02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e0eb0f00d978b4883e9f2bfd4cf5697a96d999dd6bd0ab2ba1884c59f563a88 0.600000000000 1370417 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": 913181, "vin": [ { "gen": { "height": 913171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e0eb0f00d978b4883e9f2bfd4cf5697a96d999dd6bd0ab2ba1884c59f563a88" } } ], "extra": [ 1, 225, 11, 31, 173, 60, 97, 81, 132, 160, 112, 149, 207, 43, 174, 225, 160, 185, 126, 89, 76, 236, 37, 228, 36, 145, 252, 248, 42, 219, 168, 217, 124, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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