Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33479056ec0b2cd0384ba3df211b7bb7044f0123d66104954ef62df083c7dc0e

Tx prefix hash: 257a2e9e2613fda232326802a17625d73ab289485b3af814ca5fb26e0bb8407b
Tx public key: 5a5fb297458dbebe2d08450c110404f3c86f7fbd53845c3da7b429088b02f728
Timestamp: 1720203720 Timestamp [UCT]: 2024-07-05 18:22:00 Age [y:d:h:m:s]: 01:150:04:27:59
Block: 1059239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365908 RingCT/type: yes/0
Extra: 015a5fb297458dbebe2d08450c110404f3c86f7fbd53845c3da7b429088b02f72802110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8035ac5917da039db345579e76e19166cb764d321f8ef2d25bd5d727ef64c25 0.600000000000 1529706 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": 1059249, "vin": [ { "gen": { "height": 1059239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8035ac5917da039db345579e76e19166cb764d321f8ef2d25bd5d727ef64c25" } } ], "extra": [ 1, 90, 95, 178, 151, 69, 141, 190, 190, 45, 8, 69, 12, 17, 4, 4, 243, 200, 111, 127, 189, 83, 132, 92, 61, 167, 180, 41, 8, 139, 2, 247, 40, 2, 17, 0, 0, 0, 10, 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