Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9beb9c555265d86291e2995e644d6041a2d58b1517600b9dd192e8d6997b5571

Tx prefix hash: e238713283a9747eea5133aa95825c91e70cf1f4b4e45120b281b8189c2bfa65
Tx public key: 850cd8732b53b04d80da0de6caeca06101533a09be4ec72eaa2f25dc2e86e78c
Timestamp: 1723617667 Timestamp [UCT]: 2024-08-14 06:41:07 Age [y:d:h:m:s]: 00:230:20:29:00
Block: 1087555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164850 RingCT/type: yes/0
Extra: 01850cd8732b53b04d80da0de6caeca06101533a09be4ec72eaa2f25dc2e86e78c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a9d8af5d2eb76b20219d388e1a9008b17d203a3ee197a1b333bf07ae5f1bd46 0.600000000000 1562164 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": 1087565, "vin": [ { "gen": { "height": 1087555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a9d8af5d2eb76b20219d388e1a9008b17d203a3ee197a1b333bf07ae5f1bd46" } } ], "extra": [ 1, 133, 12, 216, 115, 43, 83, 176, 77, 128, 218, 13, 230, 202, 236, 160, 97, 1, 83, 58, 9, 190, 78, 199, 46, 170, 47, 37, 220, 46, 134, 231, 140, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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