Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 026fa26fbec9552f6abe3694f46098c9a347b46877e4537a952fd38038ff7e81

Tx prefix hash: b8156b66ebe188776edaf21a6f9c329629d542264f8f5651ce17872af78819a4
Tx public key: a7b61a7c08493605e8b66e97d79bd3e0722b8cc62cf1f419839564f041d7f2dc
Timestamp: 1705426732 Timestamp [UCT]: 2024-01-16 17:38:52 Age [y:d:h:m:s]: 00:303:08:22:50
Block: 936718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217205 RingCT/type: yes/0
Extra: 01a7b61a7c08493605e8b66e97d79bd3e0722b8cc62cf1f419839564f041d7f2dc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ce1c0a1451e7c791c973ea5f936a6502741df53d1a1e869770fadb33e54fe0d 0.600000000000 1394756 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": 936728, "vin": [ { "gen": { "height": 936718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ce1c0a1451e7c791c973ea5f936a6502741df53d1a1e869770fadb33e54fe0d" } } ], "extra": [ 1, 167, 182, 26, 124, 8, 73, 54, 5, 232, 182, 110, 151, 215, 155, 211, 224, 114, 43, 140, 198, 44, 241, 244, 25, 131, 149, 100, 240, 65, 215, 242, 220, 2, 17, 0, 0, 0, 2, 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