Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6426bd2d65900bd3859651495bdf6dc4a410524a297a88660fcfe5dfb84c9514

Tx prefix hash: 5e36b116d784090f8d68b234ebfdc54cb5099da34e4423cb50000656238fb41c
Tx public key: a741787f5ca04d811cdd53cabc7b0b8be337f97505624b1fce9c157e65b20e6c
Timestamp: 1710514253 Timestamp [UCT]: 2024-03-15 14:50:53 Age [y:d:h:m:s]: 01:016:03:46:20
Block: 978931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272515 RingCT/type: yes/0
Extra: 01a741787f5ca04d811cdd53cabc7b0b8be337f97505624b1fce9c157e65b20e6c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fb17bb7e39d83a4b9241e5bafe4d0b0c484e4c54beb4ab235e14947e3114288 0.600000000000 1438960 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": 978941, "vin": [ { "gen": { "height": 978931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fb17bb7e39d83a4b9241e5bafe4d0b0c484e4c54beb4ab235e14947e3114288" } } ], "extra": [ 1, 167, 65, 120, 127, 92, 160, 77, 129, 28, 221, 83, 202, 188, 123, 11, 139, 227, 55, 249, 117, 5, 98, 75, 31, 206, 156, 21, 126, 101, 178, 14, 108, 2, 17, 0, 0, 0, 5, 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