Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378c226d6d474cf8ee59392917ee7a27903c2044b6bf955feaa09e99a8f77237

Tx prefix hash: 33a607b1124492084dcebab0a1f5f198b1d5413469574e3602f4f3403dbf9e0d
Tx public key: a4a9c92cd2c3860db1c7e6eb1e3bc9ea9b190e2f1a1d1bc5bc79490e66f4e977
Timestamp: 1713476127 Timestamp [UCT]: 2024-04-18 21:35:27 Age [y:d:h:m:s]: 01:016:22:13:33
Block: 1003464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273048 RingCT/type: yes/0
Extra: 01a4a9c92cd2c3860db1c7e6eb1e3bc9ea9b190e2f1a1d1bc5bc79490e66f4e9770211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90980d51786f3570d9253c9a6b1f07ddd523921fe63dd02f10caa020bb8b9f77 0.600000000000 1464004 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": 1003474, "vin": [ { "gen": { "height": 1003464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90980d51786f3570d9253c9a6b1f07ddd523921fe63dd02f10caa020bb8b9f77" } } ], "extra": [ 1, 164, 169, 201, 44, 210, 195, 134, 13, 177, 199, 230, 235, 30, 59, 201, 234, 155, 25, 14, 47, 26, 29, 27, 197, 188, 121, 73, 14, 102, 244, 233, 119, 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