Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41492cf2fdfb124f4fbd1766e9991b34c79f9ae8a44151be36611e661ab23c4f

Tx prefix hash: c85f1c7f01a9e8544c5b9fe6e6488b178d9500eddf3c1512d2fc1471e25da6c4
Tx public key: fe820e1b207fca701fa5af789bd42ef439ed490ceec966c724d83a8c58b66660
Timestamp: 1695571041 Timestamp [UCT]: 2023-09-24 15:57:21 Age [y:d:h:m:s]: 01:120:14:53:33
Block: 855225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347456 RingCT/type: yes/0
Extra: 01fe820e1b207fca701fa5af789bd42ef439ed490ceec966c724d83a8c58b66660021100000009faf35c9c000000000000000000

1 output(s) for total of 0.900117236000 dcy

stealth address amount amount idx
00: 013e699e9b3dadcb19b8a9872453bb91e796a8bc26c22edd5388daa2d5df35b7 0.900117236000 1309231 of 0

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": 855235, "vin": [ { "gen": { "height": 855225 } } ], "vout": [ { "amount": 900117236, "target": { "key": "013e699e9b3dadcb19b8a9872453bb91e796a8bc26c22edd5388daa2d5df35b7" } } ], "extra": [ 1, 254, 130, 14, 27, 32, 127, 202, 112, 31, 165, 175, 120, 155, 212, 46, 244, 57, 237, 73, 12, 238, 201, 102, 199, 36, 216, 58, 140, 88, 182, 102, 96, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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