Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce87d18de3596e2b58197632031b3590837cdf8e7292f029dc4df7ca27ed5d48

Tx prefix hash: c33c7200a4ed93887787e5bcd503bc6a5ede2f8acd4d44f624566aa3c055ec9f
Tx public key: 418f15214749a1f97d466f9cc60b8b081ec0589e526e9ada35c2417ab7ab4a23
Timestamp: 1705725406 Timestamp [UCT]: 2024-01-20 04:36:46 Age [y:d:h:m:s]: 01:076:13:58:46
Block: 939180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315840 RingCT/type: yes/0
Extra: 01418f15214749a1f97d466f9cc60b8b081ec0589e526e9ada35c2417ab7ab4a230211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 645ffe40e37c99bbb0f52a72beb3703b4411b5aa0ed1c3c02e033f59b2f7b66c 0.600000000000 1397268 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": 939190, "vin": [ { "gen": { "height": 939180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "645ffe40e37c99bbb0f52a72beb3703b4411b5aa0ed1c3c02e033f59b2f7b66c" } } ], "extra": [ 1, 65, 143, 21, 33, 71, 73, 161, 249, 125, 70, 111, 156, 198, 11, 139, 8, 30, 192, 88, 158, 82, 110, 154, 218, 53, 194, 65, 122, 183, 171, 74, 35, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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