Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4aa17e5393e3015db67e7ca6ef4e278198cf392f08fc1d69e9aa312880139e0

Tx prefix hash: 9429a2d5a8103439cb076f4759ce8b497fc20cda49287a404ce97af36f259eed
Tx public key: d8c2f027678842fafd4090268b06806f8ec5e33d7a6d6c29c774632e10c9fb41
Timestamp: 1696565575 Timestamp [UCT]: 2023-10-06 04:12:55 Age [y:d:h:m:s]: 01:174:09:50:26
Block: 863469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385694 RingCT/type: yes/0
Extra: 01d8c2f027678842fafd4090268b06806f8ec5e33d7a6d6c29c774632e10c9fb41021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.845218116000 dcy

stealth address amount amount idx
00: e4bf7c6a8a23c66cb1f940d819a4de16aa0241eb82d1326508d29ede594d84f7 0.845218116000 1317925 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": 863479, "vin": [ { "gen": { "height": 863469 } } ], "vout": [ { "amount": 845218116, "target": { "key": "e4bf7c6a8a23c66cb1f940d819a4de16aa0241eb82d1326508d29ede594d84f7" } } ], "extra": [ 1, 216, 194, 240, 39, 103, 136, 66, 250, 253, 64, 144, 38, 139, 6, 128, 111, 142, 197, 227, 61, 122, 109, 108, 41, 199, 116, 99, 46, 16, 201, 251, 65, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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