Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854daf19cd326c5dcb353081ed124da2339cf2a2fbbc680ae9ab1774cac72062

Tx prefix hash: b371007e7dea2503cad3b8ee516d32b58d928a1d4163f0bfb3ec04a3406f19d4
Tx public key: 438c6502c622b82803a8f9ec4db36cfe84a3c7d5f3e8fb4a57f7c9327be8344c
Timestamp: 1712567544 Timestamp [UCT]: 2024-04-08 09:12:24 Age [y:d:h:m:s]: 01:009:10:10:30
Block: 995904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267712 RingCT/type: yes/0
Extra: 01438c6502c622b82803a8f9ec4db36cfe84a3c7d5f3e8fb4a57f7c9327be8344c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1944bea094dcff00f803871d9e52882833910d8c77cc7619fdbf5d7ea2f6f1e 0.600000000000 1456318 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": 995914, "vin": [ { "gen": { "height": 995904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1944bea094dcff00f803871d9e52882833910d8c77cc7619fdbf5d7ea2f6f1e" } } ], "extra": [ 1, 67, 140, 101, 2, 198, 34, 184, 40, 3, 168, 249, 236, 77, 179, 108, 254, 132, 163, 199, 213, 243, 232, 251, 74, 87, 247, 201, 50, 123, 232, 52, 76, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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