Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5607e333f3f795f661633046e17b40059221e9b1057f625ae5450b769c432f

Tx prefix hash: 18572c6c1cf1d6dcaa9fa8e13dc924df4e4c7ea9e6ccec28c1b28abe9f85c935
Tx public key: 23c87bda634e780ca5ced74e0e47c547c26bf1efb4e89b24ccd279b63e96d565
Timestamp: 1704111191 Timestamp [UCT]: 2024-01-01 12:13:11 Age [y:d:h:m:s]: 01:059:07:05:49
Block: 925821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303462 RingCT/type: yes/0
Extra: 0123c87bda634e780ca5ced74e0e47c547c26bf1efb4e89b24ccd279b63e96d5650211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66971a4c325e6f379e3d39840b3017a9ebce26ea157c7f4348c16eac042a0827 0.600000000000 1383591 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": 925831, "vin": [ { "gen": { "height": 925821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66971a4c325e6f379e3d39840b3017a9ebce26ea157c7f4348c16eac042a0827" } } ], "extra": [ 1, 35, 200, 123, 218, 99, 78, 120, 12, 165, 206, 215, 78, 14, 71, 197, 71, 194, 107, 241, 239, 180, 232, 155, 36, 204, 210, 121, 182, 62, 150, 213, 101, 2, 17, 0, 0, 0, 5, 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